Asset management system, method, apparatus, and electronic device

ABSTRACT

This specification describes techniques for managing assets in a blockchain. One example method includes receiving, from a target user recorded in a distributed database of a blockchain network, a user input including a request to perform a contract operation on asset objects including digital assets corresponding to physical assets associated with the target user, in response to receiving the request, generating an asset container as an operation target of the contract operation, the asset container recording field information of the asset objects, generating an asset container group by dividing the asset container into the asset container group based on an association relationship between the asset objects, wherein the association relationship defines correspondences between each asset container in the asset container group and at least one other asset container in the asset container group, and performing the contract operation on the asset container group using a contract object.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/725,686, filed Dec. 23, 2019, now U.S. Pat. No. 10,691,675, which isa continuation of U.S. application Ser. No. 16/275,868, filed on Feb.14, 2019, now U.S. Pat. No. 10,691,673, which claims priority to ChinesePatent Application No. 201810151589.3, filed on Feb. 14, 2018, each ofwhich are hereby incorporated by reference in their entirety.

TECHNICAL FIELD

One or more implementations of the present specification relate to thefield of terminal technologies, and in particular, to an assetmanagement system, method, apparatus, and an electronic device.

BACKGROUND

In related technologies, any asset such as funds, bills, debts, realestate, and services owned by users (e.g., persons or enterprises) canbe securitized, so that the assets can be converted into an asset objectin a blockchain network, to improve asset liquidity.

When there are many asset objects, a separate single operation for eachasset object may not satisfy the user's efficiency demands.

SUMMARY

In view of this, one or more implementations of the presentspecification provide an asset management system, method, apparatus, andan electronic device.

To achieve the previous objective, the one or more implementations ofthe present specification provide the following technical solutions:

According to a first aspect of the one or more implementations of thepresent specification, an asset management system is provided,including: a blockchain node in a blockchain network; and assetcontainers located at the blockchain node, where the asset containersare configured to record field information of asset objects registeredon a blockchain ledger, the asset containers form at least one assetcontainer group, and an association relationship exists between eachasset container in the asset container group and at least one anotherasset container in the asset container group.

According to a second aspect of the one or more implementations of thepresent specification, an asset management method is provided,including: creating, by a blockchain node in a blockchain network, anasset container, to record field information of an asset objectregistered on a blockchain ledger; and dividing, by the blockchain node,corresponding asset containers into at least one asset container groupbased on an association relationship between asset objects, where anassociation relationship exists between each asset container in theasset container group and at least one another asset container in theasset container group.

According to a third aspect of the one or more implementations of thepresent specification, an asset management apparatus is provided,including: a creation unit, configured to enable a blockchain node in ablockchain network to create an asset container, to record fieldinformation of an asset object registered on a blockchain ledger; and adividing unit, configured to enable the blockchain node to dividecorresponding asset containers into at least one asset container groupbased on an association relationship between asset objects, where anassociation relationship exists between each asset container in theasset container group and at least one another asset container in theasset container group.

According to a fourth aspect of the one or more implementations of thepresent specification, an electronic device is provided, including: aprocessor; and a memory, configured to store an instruction that can beexecuted by the processor, where the processor is configured toimplement the asset management method according to any one of theprevious implementations.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a flowchart illustrating an asset management method, accordingto an example implementation;

FIG. 2 is a schematic diagram illustrating an asset transfer scenario,according to an example implementation;

FIG. 3 is a schematic diagram illustrating establishing an associationrelationship between asset objects, according to a first exampleimplementation;

FIG. 4 is a schematic diagram illustrating transferred asset objects,according to a first example implementation;

FIG. 5 is another schematic diagram illustrating transferred assetobjects, according to a first example implementation;

FIG. 6 is a schematic diagram illustrating establishing an associationrelationship between asset objects, according to a second exampleimplementation;

FIG. 7 is a schematic diagram illustrating transferred asset objects,according to a second example implementation;

FIG. 8 is another schematic diagram illustrating transferred assetobjects, according to a second example implementation;

FIG. 9 is a schematic diagram illustrating establishing an associationrelationship between asset objects, according to a third exampleimplementation;

FIG. 10 is a schematic diagram illustrating transferred asset objects,according to a third example implementation;

FIG. 11 is another schematic diagram illustrating transferred assetobjects, according to a third example implementation;

FIG. 12 is a schematic diagram illustrating implementing asset transfer,according to an example implementation;

FIG. 13 is a schematic diagram illustrating transferred asset objects,according to an example implementation;

FIG. 14 is a schematic structural diagram illustrating a device,according to an example implementation;

FIG. 15 is a block diagram illustrating an asset management apparatus,according to an example implementation; and

FIG. 16 is a flowchart illustrating an example of a computer-implementedmethod for asset management, according to an implementation of thepresent disclosure.

DESCRIPTION OF IMPLEMENTATIONS

Example implementations are described in detail here, and examples ofthe example implementations are presented in the accompanying drawings.When the following description relates to the accompanying drawings,unless specified otherwise, the same numbers in different accompanyingdrawings represent the same or similar elements. Implementationsdescribed in the following example implementations do not represent allimplementations consistent with one or more implementations of thepresent specification. On the contrary, the implementations are examplesof apparatuses and methods that are described in the appended claims indetail and consistent with some aspects of the one or moreimplementations of the present specification.

It is worthwhile to note that in other implementations, steps of thecorresponding method are not necessarily performed based on the sequenceshown and described in the present specification. In some otherimplementations, the method can include more steps than steps describedin the present specification. In addition, a single step described inthe present specification may be divided into a plurality of steps inother implementations for description, and a plurality of stepsdescribed in the present specification may be combined into a singlestep in other implementations for description.

FIG. 1 is a flowchart illustrating an asset management method, accordingto an example implementation. As shown in FIG. 1, the method can includethe following steps.

Step 102: A blockchain node in a blockchain network creates an assetcontainer, to record field information of an asset object registered ona blockchain ledger.

In an implementation, the blockchain ledger is used to record allinformation generated in the blockchain network. Specifically,distributed ledger technology is used in the blockchain, each blockchainnode stores full accounting information, and all blockchain nodes canreach consensus in terms of accounting information by using a consensusalgorithm. Therefore, it can be considered that all the blockchain nodesjointly maintain a uniform ledger, namely, a blockchain ledger.

In an implementation, the blockchain network can support a plurality oftypes of objects, such as an account object, and a contract object. Theaccount object is used to implement account management and relatedoperations, and the contract object is used to implement contractmanagement and related operations. Further, the blockchain network inthe present specification can support a plurality of types of assets.Therefore, the blockchain network in the present specification cansupport an asset object, to maintain and manage a corresponding type ofasset by using the asset object.

In an implementation, the asset object can include a smart asset object.The smart asset object is created for a smart asset. The smart assetcorresponds to any type of asset of users such as funds, real estate,stocks, loan contracts, bills, and accounts receivable in a real worldor offline scenario. The smart asset object enables the smart asset tobe processed in the block chain, for example, the smart asset isparticularly suitable for processing the smart asset object by using asmart contract in the block chain.

In an implementation, the blockchain node creates an asset container, sothat field information of an asset object can be recorded in the assetcontainer. Therefore, the corresponding asset object is maintained basedon the asset container. For example, the asset container can include adata table of a predetermined structure, etc. Implementations are notlimited in the present specification.

In an implementation, the blockchain node can create a contractoperation based on a contract object corresponding to a specified typeof asset by invoking an asset described in the contract object, tocreate an asset object satisfying the specified type. In anotherimplementation, the blockchain node can further create a contract objectin other ways. Implementations are not limited in the presentspecification.

104. The blockchain node divides corresponding asset containers into atleast one asset container group based on an association relationshipbetween asset objects, where an association relationship exists betweeneach asset container in the asset container group and at least oneanother asset container in the asset container group.

In an implementation, unified maintenance can be performed on aplurality of associated asset containers in the asset container groupbased on an association relationship between asset containers in theasset container group, to implement batch management of correspondingasset objects. Therefore, there is no need to perform separatemanagement on each asset object, so that asset object managementefficiency of the blockchain network can be improved.

In an implementation, the blockchain node can initiate an operationinstruction for the first asset container in the asset container group.Correspondingly, when there is the second asset container associatedwith the first asset container in the asset container group, both thefirst asset container and the second asset container are added asoperation targets of the operation instruction. The blockchain node caninitiate the operation instruction for the first asset container, andthere is no request to separately initiate the operation instruction forthe first asset container and the second asset container. Particularly,there may be a large quantity of second asset containers in the assetcontainer group. Based on the previous implementation, a large quantityof operations such as selecting the second asset container and sendingthe operation instruction can be omitted, and corresponding operationprocessing can be rapidly and accurately performed for the first assetcontainer and all the second asset containers.

In an implementation, the blockchain node initiates an operationinstruction for the first asset container in the asset container group.Correspondingly, after the operation instruction is executed for thefirst asset container, the second asset container and the first assetcontainer keep an original association relationship. For example, whenthe operation instruction is an asset object transfer instruction, theblockchain node only requests to transfer the first asset container to atarget object (e.g., an account object, a contract object, or an assetobject) by using the asset object transfer instruction, and it can beconsidered that the second asset container is also transferred to thetarget object based on the association relationship between the secondasset container and the first asset container. Therefore, there is norequest to separately initiate the asset object transfer instruction forthe first asset container and the second asset container. Particularly,the asset container group may include a large quantity of second assetcontainers. Based on the previous implementation, a large quantity ofoperations such as selecting the second asset container and sending theoperation instruction can be omitted, and corresponding operationprocessing can be rapidly and accurately performed for the first assetcontainer and all the second asset containers.

In an implementation, the previous operation instruction can include anytype of instruction, for example, the previous asset object transferinstruction that is used to transfer an asset object, or an asset objecttransaction instruction that is used for asset object transaction.Implementations are not limited in the present specification.

In an implementation, the blockchain node can initiate the previousoperation instruction in any way. Implementations are not limited in thepresent specification. For example, the blockchain node can initiate acontract operation for the first asset container, so that correspondingoperation processing can be performed on the first asset container andthe second asset container. The contract operation can be written to acorresponding contract object in advance. If the blockchain node has aninvoking permission for the contract operation, the previous operationinstruction can be initiated based on the contract operation.

In an implementation, the association relationship between assetcontainers can be in a plurality of forms. Implementations are notlimited in the present specification. For example, there can be abinding relationship between a plurality of asset containers. When theblockchain node initiates an operation instruction for any one of theplurality of asset containers, the asset container can be used as thefirst asset container in the previous implementation, and remainingasset containers in the plurality of asset containers can be used as thesecond asset containers, to implement processing operations in theprevious implementation. For another example, there can be a homingrelationship of a hierarchical structure between a plurality of assetcontainers. When there is an association relationship between the firstasset container and the second asset container, it can be consideredthat the lower-level second asset container belongs to the higher-levelfirst asset container. For example, the second asset container caninclude all direct descendant asset containers of the first assetcontainer in a corresponding asset container group. For example, ifasset container A1 is the first asset container, both asset containersB1 and B2 are child asset containers of asset container A1, and assetcontainer C is a child asset container of asset container B1, assetcontainers B1 and B2 and asset container C are direct descendant assetcontainers of asset container A1 and are the previously described secondasset containers. If asset container A1 and asset container A2 are childasset containers of asset container X, and asset container B3 is a childasset container of asset container A2, asset container B3 is not adirect descendant asset container of asset container A1 and is not thepreviously described second asset container.

In an implementation, because an object that an asset object belongs tois determined, for an asset container in the blockchain network, eachparent asset container can have one or more child asset containers, buteach child asset container belongs to only one parent asset container.

In an implementation, when the second asset container is an assetcontainer associated with the first asset container in the assetcontainer group, indication information of the second asset container isrecorded in the first asset container, so that an associationrelationship between the first asset container and the second assetcontainer is determined based on the indication information. Forexample, the indication information can include an address of the secondasset container. The indication information can be added to apredetermined field of an asset object that is recorded in the firstasset container, so that the indication information can be read from thepredetermined field in the first asset container when an operationinstruction is initiated for the first asset container and correspondingprocessing operations is performed for the first asset container, todetermine the associated second asset container. In some implementation,the association relationship between the first asset container and thesecond asset container can be recorded in other ways. Implementationsare not limited in the present specification. For example, theblockchain node can create a relationship container, and associationrelationship information of asset containers is recorded in therelationship container.

For ease of understanding, the following describes the technicalsolutions of the one or more implementations of the presentspecification by using an “asset transfer” process as an example. FIG. 2is a schematic diagram illustrating an asset transfer scenario,according to an example implementation. As shown in FIG. 2, assume thatuser 1 registers account U1 at a blockchain network, and user 2registers account U2 at the blockchain network. An asset address fieldof account U1 includes address D1 corresponding to asset object A1,address D2 corresponding to asset object A2, and address D3corresponding to asset object A3. It indicates that asset object A1,asset object A2, and asset object A3 belong to account U1. An assetaddress field of account U2 includes address D4 corresponding to assetobject A4. It indicates that asset object A4 belongs to account U2. Whenuser 1 wants to transfer asset object A1, asset object A2, and assetobject A3 corresponding to account U1 to account U2, quick assettransfer can be implemented by using the asset management solution ofthe present specification.

It is worthwhile to note that a blockchain node in the blockchainnetwork respectively creates asset containers corresponding to assetobjects A1 to A4, to record field information such as asset addressfields, storage information fields, contract content fields, andanti-replay attack count fields of asset objects A1 to A4. In terms offunction and processing logic, it can still be considered thatimplementation is performed based on an asset object. Therefore, forease of understanding, the following performs description by using“asset object” instead of a corresponding asset container.

FIG. 3 is a schematic diagram illustrating establishing an associationrelationship between asset objects, according to a first exampleimplementation. As shown in FIG. 3, a blockchain node in a blockchainnetwork can configure asset object A2 and asset object A3 as assetobjects belonging to asset object A1, to establish an associationrelationship of a hierarchical structure between asset objects A1 to A3.Asset object A1 is used as a parent asset object (corresponding to aparent asset container), and asset objects A2 and A3 are used as childasset objects (corresponding to child asset containers). Specifically,the blockchain node can write address D2 of asset object A2 to an assetaddress field of asset object A1, so that asset object A2 is configuredas a child asset object belonging to asset object A1. Similarly, theblockchain node can write address D3 of asset object A3 to the assetaddress field of asset object A1, so that asset object A3 is configuredas a child asset object belonging to asset object A1. In this case, itcan be understood that ownership of asset object A1 directly belongs toaccount U1, and because ownership of asset objects A2 and A3 belongs toasset object A1, the ownership of asset objects A2 and A3 indirectlybelongs to account U1.

Therefore, an asset object transfer instruction only requests to be sentfor asset object A1, and asset object A1 is transferred to account U2.Then, asset objects A2 and A3 are automatically transferred based on anassociation relationship between asset object A1 and asset objects A2and A3. For example, FIG. 4 is a schematic diagram illustratingtransferred asset objects, according to a first example implementation.As shown in FIG. 4, an asset object transfer instruction is initiatedfor asset object A1, address D1 can be deleted from an asset addressfield of account U1, and address D1 is added to an asset address fieldof account U2, to transfer ownership of asset object A1 from account U1to account U2. In this case, because ownership of asset objects A2 andA3 belongs to asset object A1, the ownership of asset objects A2 and A3indirectly belongs to account U2, and the ownership of asset objects A2and A3 is automatically transferred based on an association relationshipbetween asset object A1 and asset objects A2 and A3 without separatelyinitiating the corresponding asset object transfer instruction for assetobject A2 and asset object A3.

For another example, FIG. 5 is another schematic diagram illustratingtransferred asset objects, according to a first example implementation.As shown in FIG. 5, an asset object transfer instruction is initiatedfor asset object A1, address D1 can be deleted from an asset addressfield of account U1, and address D1 is added to an asset address fieldof asset object A4. Because ownership of asset object A4 belongs toaccount U2, ownership of asset object A1 is transferred from account U1to account U2. In this case, because ownership of asset objects A2 andA3 belongs to asset object A1, the ownership of asset objects A2 and A3indirectly belongs to account U2, and the ownership of asset objects A2and A3 is automatically transferred based on an association relationshipbetween asset object A1 and asset objects A2 and A3 without separatelyinitiating the corresponding asset object transfer instruction for assetobject A2 and asset object A3.

In addition to the association relationship shown in FIG. 3, other formsof association relationship can be established for asset objects A1 toA3. Implementations are not limited in the present specification. Forexample, FIG. 6 is a schematic diagram illustrating establishing anassociation relationship between asset objects, according to a secondexample implementation. As shown in FIG. 6, a blockchain node can writeaddress D2 of asset object A2 to an asset address field of asset objectA1, so that asset object A2 is configured as a child asset objectbelonging to asset object A1. Similarly, the blockchain node can writeaddress D3 of asset object A3 to an asset address field of asset objectA2, so that asset object A3 is configured as a child asset objectbelonging to asset object A2. In this case, it can be understood thatownership of asset object A1 directly belongs to account U1, and becauseownership of asset object A2 belongs to asset object A1, and ownershipof asset object A3 belongs to asset object A2, ownership of assetobjects A2 and A3 indirectly belongs to account U1.

Therefore, an asset object transfer instruction only requests to be sentfor asset object A1, and asset object A1 is transferred to account U2.Then, asset objects A2 and A3 are automatically transferred based on anassociation relationship between asset object A1 and asset objects A2and A3. For example, similar to the implementation shown in FIG. 4, FIG.7 is a schematic diagram illustrating transferred asset objects,according to a second example implementation. As shown in FIG. 7, anasset object transfer instruction is initiated for asset object A1,address D1 can be deleted from an asset address field of account U1, andaddress D1 is added to an asset address field of account U2, to transferownership of asset object A1 from account U1 to account U2. In thiscase, because ownership of asset objects A2 belongs to asset object A1,and ownership of asset object A3 belongs to asset object A2, ownershipof asset objects A2 and A3 indirectly belongs to account U2, and theownership of asset objects A2 and A3 is automatically transferred basedon an association relationship between asset object A1 and asset objectsA2 and A3 without separately initiating the corresponding asset objecttransfer instruction for asset object A2 and asset object A3.

For another example, similar to the implementation shown in FIG. 5, FIG.8 is another schematic diagram illustrating transferred asset objects,according to a second example implementation. As shown in FIG. 8, anasset object transfer instruction is initiated for asset object A1,address D1 can be deleted from an asset address field of account U1, andaddress D1 is added to an asset address field of asset object A4.Because ownership of asset object A4 belongs to account U2, ownership ofasset object A1 is transferred from account U1 to account U2. In thiscase, because ownership of asset objects A2 belongs to asset object A1,and ownership of asset object A3 belongs to asset object A2, ownershipof asset objects A2 and A3 indirectly belongs to account U2, and theownership of asset objects A2 and A3 is automatically transferred basedon an association relationship between asset object A1 and asset objectsA2 and A3 without separately initiating the corresponding asset objecttransfer instruction for asset object A2 and asset object A3.

FIG. 9 is a schematic diagram illustrating establishing an associationrelationship between asset objects, according to a third exampleimplementation. As shown in FIG. 9, a blockchain node can create newasset object A5, write address D5 of asset object A5 to an asset addressfield of account U1, and write addresses D1 to D3 of asset object A1 toA3 to an asset address field of asset object A5, so that asset objectsA1 to A3 are configured as child asset objects belonging to asset objectA5. In this case, it can be understood that ownership of asset object A5directly belongs to account U1, and because ownership of asset objectsA1 to A3 belongs to asset object A5, the ownership of asset objects A1to A3 indirectly belongs to account U1.

Therefore, an asset object transfer instruction only requests to be sentfor asset object A5, and asset object A5 is transferred to account U2.Then, asset objects A1 to A3 are automatically transferred based on anassociation relationship between asset object A5 and asset objects A1 toA3. For example, similar to the implementations shown in FIG. 4 and FIG.7, FIG. 10 is a schematic diagram illustrating transferred assetobjects, according to a third example implementation. As shown in FIG.10, an asset object transfer instruction is initiated for asset objectA5, address D5 can be deleted from an asset address field of account U1,and address D5 is added to an asset address field of account U2, totransfer ownership of asset object A5 from account U1 to account U2. Inthis case, because ownership of asset objects A1 to A3 belongs to assetobject A5, the ownership of asset objects A1 to A3 indirectly belongs toaccount U2, and the ownership of asset objects A1 to A3 is automaticallytransferred based on an association relationship between asset object A5and asset objects A1 to A3 without separately initiating thecorresponding asset object transfer instruction for asset objects A1 toA3.

For another example, similar to the implementations shown in FIG. 5 andFIG. 8, FIG. 11 is another schematic diagram illustrating transferredasset objects, according to a third example implementation. As shown inFIG. 11, an asset object transfer instruction is initiated for assetobject A5, address D5 can be deleted from an asset address field ofaccount U1, and address D5 is added to an asset address field of assetobject A4. Because ownership of asset object A4 belongs to account U2,ownership of asset object A5 is transferred from account U1 to accountU2. In this case, because ownership of asset objects A1 to A3 belongs toasset object A5, the ownership of asset objects A1 to A3 indirectlybelongs to account U2, and the ownership of asset objects A1 to A3 isautomatically transferred based on an association relationship betweenasset object A5 and asset objects A1 to A3 without separately initiatingthe corresponding asset object transfer instruction for asset objects A1to A3.

In the implementation shown in FIG. 3, asset object A1 has the highestlevel, and asset objects A2 and A3 have the same relatively lower level.Similarly, in the implementation shown in FIG. 9, asset object A5 hasthe highest level, and asset objects A1 to A3 have the same relativelylower level. In the implementation shown in FIG. 6, levels of assetobject A1, asset object A2, and asset object A3 are in descending order.In some scenarios, when there are more asset objects involved, a createdassociation relationship between the asset objects can include one ormore cases in the previous implementation. For example, when there areasset objects B1 to B4, levels of asset object B1, asset object B2,asset object B3 can be in descending order, and asset object B2 andasset object B4 have the same level.

In the previous implementations shown in FIG. 3 to FIG. 11, addressinformation of a child asset object is written to an asset address fieldof a parent asset object, to create an association relationship betweenvarious asset objects. In other implementations, an associationrelationship between asset objects can be created in other ways.Implementations are not limited in the present specification. Forexample, FIG. 12 is a schematic diagram illustrating implementing assettransfer, according to an example implementation. As shown in FIG. 12,addresses D1 to D3 corresponding to asset objects A1 to A3 are writtento an asset address field of account U1. It indicates that ownership ofasset objects A1 to A3 belongs to account U1. An associationrelationship between asset objects A1 to A3 can be recorded in an assetrelationship field (for example, the asset relationship field can beincluded in the previous information storage field or another field)corresponding to account U1. For example, the association relationshipcan be “address D1-address D2” and “address D1-address D3”. It indicatesthat asset objects A2 and A3 are configured as child asset objectsbelonging to asset object A1. The association relationship correspondsto the association relationship in the implementation shown in FIG. 3.

FIG. 13 is a schematic diagram illustrating transferred asset objects,according to an example implementation. As shown in FIG. 13, an assetobject transfer instruction is initiated for asset object A1, address D1can be deleted from an asset address field of account U1, and address D1is added to an asset address field of account U2, to transfer ownershipof asset object A1 from account U1 to account U2. In this case, assetobject A2 and asset object A3 are automatically configured as operationtargets of the asset object transfer instruction based on an associationrelationship “address D1-address D2” and “address D1-address D3”recorded in an asset relationship field of account U1, so that addressD2 is deleted from the asset address field of account U1, address D2 isadded to the asset address field of account U2, address D3 is deletedfrom the asset address field of account U1, and address D3 is added tothe asset address field of account U2. Therefore, ownership of assetobjects A2 and A3 is automatically transferred based on the associationrelationship between asset objects A1 to A3 without separatelyinitiating the corresponding asset object transfer instruction for assetobjects A2 and A3.

In addition to transferring asset objects A1 to A3 from account U1 toaccount U2, the association relationship between asset objects A1 to A3can also be transferred from the asset relationship field of account U1to an asset relationship field of account U2, so that a quick assetobject transfer operation can be subsequently implemented based on theassociation relationship. In some implementation, the previous assetrelationship can be configured as a fixed attribute that cannot bemodified between asset objects, or can be adjusted based on an actualsituation, and this depends on a used specified logic.

In some implementation, in addition to transferring address D1 of assetobject A1 to the asset address field of account U2, address D1 can alsobe transferred to an asset address field of asset object A4, so that theownership of asset object A1 is transferred from account U1 to assetobject A4. In this case, the ownership of asset objects A2 and A3 canalso be transferred from account U1 to asset object A4 based on theassociation relationship between asset object A1 and asset objects A2and A3. Similarly, the association relationship between asset objects A1to A3 can be transferred from the asset relationship field of account U1to an asset relationship field of asset object A4.

FIG. 14 is a schematic structural diagram illustrating a device,according to an example implementation. Referring to FIG. 14, in termsof hardware, the device includes a processor 1402, a local bus 1404, anetwork interface 1406, a memory 1408, and a non-volatile memory 1410.In some implementation, the device may further include hardware neededby other services. The processor 1402 reads a corresponding computerprogram from the non-volatile memory 1410 to the memory 1408 forrunning, and an asset management apparatus is logically formed. In someimplementation, in addition to a software implementation, one or moreimplementations of the present specification do not exclude otherimplementations, for example, a logic device or a combination ofhardware and software. In other words, an execution body of thefollowing processing procedure is not limited to various logical units,and can also be hardware or a logic device.

Referring to FIG. 15, in a software implementation, the asset managementapparatus can include: a creation unit 1501, configured to enable ablockchain node in a blockchain network to create an asset container, torecord field information of an asset object registered on a blockchainledger; and a dividing unit 1502, configured to enable the blockchainnode to divide corresponding asset containers into at least one assetcontainer group based on an association relationship between assetobjects, where an association relationship exists between each assetcontainer in the asset container group and at least one another assetcontainer in the asset container group.

Optionally, the asset management apparatus further includes: aninstruction initiation unit 1503, configured to enable the blockchainnode to initiate an operation instruction for the first asset containerin the asset container group.

When there is the second asset container associated with the first assetcontainer in the asset container group, both the first asset containerand the second asset container are added as operation targets of theoperation instruction.

Optionally, the asset management apparatus further includes: aninstruction initiation unit 1503, configured to enable the blockchainnode to initiate an operation instruction for the first asset containerin the asset container group.

After the operation instruction is executed for the first assetcontainer, the second asset container and the first asset container keepan original association relationship.

Optionally, the instruction initiation unit is specifically configuredto enable the blockchain node to initiate a contract operation for thefirst asset container.

Optionally, the operation instruction includes at least one of an assetobject transfer instruction and an asset object transaction instruction.

Optionally, the second asset container includes all direct descendantasset containers of the first asset container in the asset containergroup.

Optionally, the association relationship includes a homing relationshipof a hierarchical structure.

Optionally, each parent asset container has one or more child assetcontainers, and each child asset container belongs to only one parentasset container.

Optionally, when the second asset container is an asset containerassociated with the first asset container in the asset container group,indication information of the second asset container is recorded in thefirst asset container.

Optionally, the indication information includes an address of the secondasset container.

Optionally, the indication information is added to a predetermined fieldof an asset object recorded in the first asset container.

The system, apparatuses, modules, or units illustrated in the previousimplementations can be implemented by using a computer chip or anentity, or can be implemented by using a product having a particularfunction. A typical implementation device is a computer, and thecomputer can be a personal computer, a laptop computer, a cellularphone, a camera phone, a smartphone, a personal digital assistant, amedia player, a navigation device, an email receiving and sendingdevice, a game console, a tablet computer, a wearable device, or anycombination of these devices.

In a typical configuration, a computer includes one or more processors(CPU), an input/output interface, a network interface, and a memory.

The memory may include a non-persistent memory, a random access memory(RAM), and/or a non-volatile memory in a computer readable medium, forexample, a read-only memory (ROM) or a flash memory (flash RAM). Thememory is an example of the computer readable medium.

The computer readable medium includes persistent, non-persistent,movable, and unmovable media that can implement information storage byusing any method or technology. Information can be a computer readableinstruction, a data structure, a program module, or other data. Acomputer storage medium includes but is not limited to a phase-changerandom access memory (PRAM), a static random access memory (SRAM), adynamic random access memory (DRAM), a random access memory (RAM) ofanother type, a read-only memory (ROM), an electrically erasableprogrammable read-only memory (EEPROM), a flash memory or another memorytechnology, a compact disc read-only memory (CD-ROM), a digitalversatile disc (DVD) or another optical storage, a magnetic tape, amagnetic disk storage, a quantum memory, a graphene storage medium oranother magnetic storage device or any other non-transmission medium.The computer storage medium can be used to store information that can beaccessed by a computing device. Based on the definition in the presentspecification, the computer readable medium does not include transitorycomputer-readable media (transitory media), for example, a modulateddata signal and carrier.

It is worthwhile to further note that the terms “include”, “comprise”,or their any other variant is intended to cover a non-exclusiveinclusion, so that a process, a method, a product, or a device thatincludes a list of elements not only includes those elements but alsoincludes other elements which are not expressly listed, or furtherincludes elements inherent to such a process, a method, a product, or adevice. An element preceded by “includes a . . . ” does not, withoutmore constraints, preclude the existence of additional identicalelements in the process, method, product, or device that includes theelement.

Specific implementations of the present specification are describedabove. Other implementations fall within the scope of the appendedclaims. In some cases, the actions or steps described in the claims canbe performed in an order different from the order in the implementationand the desired results can still be achieved. In addition, the processprovided in the accompanying drawings does not necessarily require aparticular execution order to achieve the desired results. In someimplementations, multi-tasking and parallel processing can beadvantageous.

The terms used in the one or more implementations of the presentspecification are merely for illustrating specific implementations, andare not intended to limit the one or more implementations of the presentspecification. The terms “a”, “said”, and “the” of singular forms usedin the one or more implementations of the present specification and theappended claims are also intended to include plural forms, unlessotherwise specified in the context clearly. It should also be understoodthat the term “and/or” used in the present specification indicates andincludes any or all possible combinations of one or more associatedlisted items.

It should be understood that although terms “first”, “second”, “third”,etc. may be used in the one or more implementations of the presentspecification to describe various types of information, the informationis not limited to the terms. These terms are used to differentiateinformation of the same type. For example, without departing from thescope of the one or more implementations of the present specification,the first information can also be referred to as the second information,and similarly, the second information can also be referred to as thefirst information. Depending on the context, for example, the word “if”used here can be explained as “while”, “when”, or “in response todetermining”.

The previous descriptions are example implementations of the one or moreimplementations of the present specification, but are not intended tolimit the one or more implementations of the present specification. Anymodification, equivalent replacement, improvement, etc. made withoutdeparting from the spirit and principle of the one or moreimplementations of the present specification shall fall within theprotection scope of the one or more implementations of the presentspecification.

FIG. 16 is a flowchart illustrating an example of a computer-implementedmethod 1600 for management of assets in a blockchain, according to animplementation of the present disclosure. For clarity of presentation,the description that follows generally describes method 1600 in thecontext of the other figures in this description. However, it will beunderstood that method 1600 can be performed, for example, by anysystem, environment, software, and hardware, or a combination ofsystems, environments, software, and hardware, as appropriate. In someimplementations, various steps of method 1600 can be run in parallel, incombination, in loops, or in any order.

At 1602, keys are generated for a target user recorded in a distributeddatabase of the blockchain network. The keys include a public key and aprivate key. In some implementations, the public key is associated withan account address of an institution in the blockchain. The private keycan be configured to be used by the institution to operate the account.In some implementations, the blockchain network includes a consortiumchain, and the target member (user) in the blockchain network is aconsortium member that has asset object generation authority in theconsortium chain. The blockchain network includes one or more accountobjects and one or more contract objects. The objects of the blockchainnetwork (e.g., account objects, contract objects, target objects, andasset objects) include one or more fields. For example, the fields caninclude one or more of the following: the IP configuration for thetarget user; DNS logs from the target user, including events such as DNSlookups, changes to DNS settings, and so forth; network firewall logs(and/or other security-related log files) from the target user,including events such as blocked or allowed network communications, andso forth; operating system (OS) logs from the target user, includingevents associated with the OS; port settings on the target user; useraccess logs from the target user, including successful and/orunsuccessful user attempts to transfer assets from or to the targetuser; and/or user privilege data from the target user, includingparticular access privileges for various users on the target user. Thefields can also include one or more of an entity name, entity ID, targetuser ID, OS version information, and software version(s) for installedsoftware, network router information, other DNS settings, firewallsettings, port settings, IP whitelist and/or blacklist settings, and soforth. From 1602, method 1600 proceeds to 1604.

At 1604, a user input is received from the target user. The user inputincludes a request to perform a contract operation on asset objects. Theasset objects include digital assets corresponding to physical assetsassociated with the target user. From 1604, method 1600 proceeds to1606.

At 1606, a contract object corresponding to the asset objects isdetermined through a selection of contract objects from the blockchainnetwork. The contract object can include an execution program configuredto generate the target object and a code field that is used to maintainan execution code related to the execution program. The contract objectcan include an operation instruction used to perform the contractoperation on the asset container group, maintaining associationrelationships of the asset container group. The contract object caninclude a code field that is used to maintain an execution code relatedto the execution program. From 1606, method 1600 proceeds to 1608.

At 1608, in response to receiving the request, an asset container isgenerated based on the asset objects. The asset container can begenerated to serve as an operation target of the contract operation. Theasset container can record field information of the asset objects. Theasset container can include a data table of a predetermined structure.In some implementations, the asset container is a parent asset containerthat has one or more child asset containers, and each child assetcontainer belongs to only one parent asset container. For example, asecond asset container can be generated in response to generating theasset container. The second asset container can be a direct descendantasset container of the first asset container. From 1608, method 1600proceeds to 1610.

At 1610, an asset container group is generated by dividing the assetcontainer based on an association relationship between the asset objectswithin the asset container. The association relationship can definecorrespondences between each asset container in the asset containergroup and at least one other asset container in the asset containergroup. The association relationship can include a homing relationship ofa hierarchical structure. From 1610, method 1600 proceeds to 1612.

At 1612, a contract operation is performed using the contract object.For example, the contract object performs the contract operation byexecuting the operation instruction. The operation instruction caninclude a transfer instruction or a transaction instruction for at leastone of the asset objects. In some implementations, the contractoperation includes updating a target object associated with the assetobjects. The target object includes an address field used to maintainaddress information of the plurality of asset objects by deploying acontract object corresponding to the asset type in the blockchain tocreate the target object. After 1612, method 1600 stops.

Implementations of the present application can solve technical problemsin managing assets in a blockchain. In some implementations, theblockchain is a distributed storage solution that provides immutable andtamper-resistant data transfer and storage, and the data is stored in adatabase of the blockchain in an encrypted form. Such security measuresensure that that system state data stored on the blockchain is notcorrupted or altered by malicious processes. For example, an alterationof an asset-receiving object can be a tactic used by an attacker when atarget user is compromised for fraudulent purposes, and storage ofsystem state data on an immutable blockchain prevents the use of thattactic by an attacker. In some implementations, the blockchain headersfrom different payment applications across entities are cross-Merkelizedor otherwise processed on the blockchain to further ensure the integrityof the data stored in the database of the blockchain.

In consideration of security and confidentiality, contract objects canbe configured to perform privacy protection processing on the dataassociated with the asset object before generating the asset object andsending the address information to other platforms for processing. Inaddition, the asset transfer operation is configured such that it doesnot affect the overall data volume within the blockchain by deleting adata volume from a first location when adding the corresponding datavolume in a second location. As such, the asset transfer operation doesnot lead to an exponential increase of data volume, which is a commonproblem associated with conventional methods of asset management.

Implementations of the present application provide methods andapparatuses for improving asset management. In some implementations, aprocessing platform (e.g., a payment processing server) obtains datathat is to be validated and that corresponds to a predetermined featurefrom a data providing platform as a data group that is to be validated(e.g., a data group that corresponds to user transaction amounts). Inaddition, the processing platform can further obtain additional (e.g.,historical) data associated with the asset that is to be validated bythe predetermined transfer rule. The historical data may also correspondto the same predetermined feature, and the comparison data group can beprovided to a processing platform (e.g., a node of the blockchainnetwork) for processing before the asset transfer. Then, the processingplatform determines whether the asset transfer request satisfies thepredetermined transfer rule. If the predetermined transfer rule issatisfied (e.g., there is no abnormal data), the processing platform cancontinue to transfer the asset. If the processing platform determinesthat there is abnormal data, the processing platform can start alerting,instruct related persons to analyze the cause of the data exception, andtrigger related solutions.

In some implementations, the processing platform determines risk scoresof asset transfers and transactions across multiple different entities,based on both transaction data for the transaction and system state datafor the hosts involved in handling the transaction. The risk scores areexamined to identify those transactions that are deemed high risk, withabove-threshold scores. Such transactions can be blocked or queued forfurther examination in a case management system, for example. The systemstate data to be used for comparison, as well as the transaction dataand risk score(s), can be stored on the blockchain that providesimmutable, secure, and distributed data storage. Use of the blockchainfacilitates the collection and analysis of a large amount of transactiondata and system state data, which may grow over time as transactiontraffic increases and/or transaction networks expand by adding morehosts to accommodate the increased traffic. Accordingly, through the useof a blockchain to store and analyze the data, implementations providescalability with respect to the data extraction, analysis, and storageof the data. Moreover, because the blockchain is distributed acrossmultiple network locations, implementations avoid the use of acentralized database for data storage and are therefore less vulnerableto corruption or deletion by malicious processes, in comparison totraditional, previously available risk analysis solutions that arevulnerable to attack at such a centralized storage hub.

Embodiments and the operations described in this specification can beimplemented in digital electronic circuitry, or in computer software,firmware, or hardware, including the structures disclosed in thisspecification or in combinations of one or more of them. The operationscan be implemented as operations performed by a data processingapparatus on data stored on one or more computer-readable storagedevices or received from other sources. A data processing apparatus,computer, or computing device may encompass apparatus, devices, andmachines for processing data, including by way of example a programmableprocessor, a computer, a system on a chip, or multiple ones, orcombinations, of the foregoing. The apparatus can include specialpurpose logic circuitry, for example, a central processing unit (CPU), afield programmable gate array (FPGA) or an application-specificintegrated circuit (ASIC). The apparatus can also include code thatcreates an execution environment for the computer program in question,for example, code that constitutes processor firmware, a protocol stack,a database management system, an operating system (for example anoperating system or a combination of operating systems), across-platform runtime environment, a virtual machine, or a combinationof one or more of them. The apparatus and execution environment canrealize various different computing model infrastructures, such as webservices, distributed computing and grid computing infrastructures.

A computer program (also known, for example, as a program, software,software application, software module, software unit, script, or code)can be written in any form of programming language, including compiledor interpreted languages, declarative or procedural languages, and itcan be deployed in any form, including as a stand-alone program or as amodule, component, subroutine, object, or other unit suitable for use ina computing environment. A program can be stored in a portion of a filethat holds other programs or data (for example, one or more scriptsstored in a markup language document), in a single file dedicated to theprogram in question, or in multiple coordinated files (for example,files that store one or more modules, sub-programs, or portions ofcode). A computer program can be executed on one computer or on multiplecomputers that are located at one site or distributed across multiplesites and interconnected by a communication network.

Processors for execution of a computer program include, by way ofexample, both general- and special-purpose microprocessors, and any oneor more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read-only memory ora random-access memory or both. The essential elements of a computer area processor for performing actions in accordance with instructions andone or more memory devices for storing instructions and data. Generally,a computer will also include, or be operatively coupled to receive datafrom or transfer data to, or both, one or more mass storage devices forstoring data. A computer can be embedded in another device, for example,a mobile device, a personal digital assistant (PDA), a game console, aGlobal Positioning System (GPS) receiver, or a portable storage device.Devices suitable for storing computer program instructions and datainclude non-volatile memory, media and memory devices, including, by wayof example, semiconductor memory devices, magnetic disks, andmagneto-optical disks. The processor and the memory can be supplementedby, or incorporated in, special-purpose logic circuitry.

Mobile devices can include handsets, user equipment (UE), mobiletelephones (for example, smartphones), tablets, wearable devices (forexample, smart watches and smart eyeglasses), implanted devices withinthe human body (for example, biosensors, cochlear implants), or othertypes of mobile devices. The mobile devices can communicate wirelessly(for example, using radio frequency (RF) signals) to variouscommunication networks (described below). The mobile devices can includesensors for determining characteristics of the mobile device's currentenvironment. The sensors can include cameras, microphones, proximitysensors, GPS sensors, motion sensors, accelerometers, ambient lightsensors, moisture sensors, gyroscopes, compasses, barometers,fingerprint sensors, facial recognition systems, RF sensors (forexample, Wi-Fi and cellular radios), thermal sensors, or other types ofsensors. For example, the cameras can include a forward- or rear-facingcamera with movable or fixed lenses, a flash, an image sensor, and animage processor. The camera can be a megapixel camera capable ofcapturing details for facial and/or iris recognition. The camera alongwith a data processor and authentication information stored in memory oraccessed remotely can form a facial recognition system. The facialrecognition system or one-or-more sensors, for example, microphones,motion sensors, accelerometers, GPS sensors, or RF sensors, can be usedfor user authentication.

To provide for interaction with a user, embodiments can be implementedon a computer having a display device and an input device, for example,a liquid crystal display (LCD) or organic light-emitting diode(OLED)/virtual-reality (VR)/augmented-reality (AR) display fordisplaying information to the user and a touchscreen, keyboard, and apointing device by which the user can provide input to the computer.Other kinds of devices can be used to provide for interaction with auser as well; for example, feedback provided to the user can be any formof sensory feedback, for example, visual feedback, auditory feedback, ortactile feedback; and input from the user can be received in any form,including acoustic, speech, or tactile input. In addition, a computercan interact with a user by sending documents to and receiving documentsfrom a device that is used by the user; for example, by sending webpages to a web browser on a user's client device in response to requestsreceived from the web browser.

Embodiments can be implemented using computing devices interconnected byany form or medium of wireline or wireless digital data communication(or combination thereof), for example, a communication network. Examplesof interconnected devices are a client and a server generally remotefrom each other that typically interact through a communication network.A client, for example, a mobile device, can carry out transactionsitself, with a server, or through a server, for example, performing buy,sell, pay, give, send, or loan transactions, or authorizing the same.Such transactions may be in real time such that an action and a responseare temporally proximate; for example an individual perceives the actionand the response occurring substantially simultaneously, the timedifference for a response following the individual's action is less than1 millisecond (ms) or less than 1 second (s), or the response is withoutintentional delay taking into account processing limitations of thesystem.

Examples of communication networks include a local area network (LAN), aradio access network (RAN), a metropolitan area network (MAN), and awide area network (WAN). The communication network can include all or aportion of the Internet, another communication network, or a combinationof communication networks. Information can be transmitted on thecommunication network according to various protocols and standards,including Long Term Evolution (LTE), 5G, IEEE 802, Internet Protocol(IP), or other protocols or combinations of protocols. The communicationnetwork can transmit voice, video, biometric, or authentication data, orother information between the connected computing devices.

Features described as separate implementations may be implemented, incombination, in a single implementation, while features described as asingle implementation may be implemented in multiple implementations,separately, or in any suitable sub-combination. Operations described andclaimed in a particular order should not be understood as requiring thatthe particular order, nor that all illustrated operations must beperformed (some operations can be optional). As appropriate,multitasking or parallel-processing (or a combination of multitaskingand parallel-processing) can be performed.

What is claimed is:
 1. A computer-implemented method for asset management, the computer-implemented method comprising: receiving, from a target user recorded in a distributed database of a blockchain network, a user input comprising a request to perform a contract operation on asset objects comprising digital assets corresponding to physical assets associated with the target user; in response to receiving the request, generating an asset container as an operation target of the contract operation, the asset container recording field information of the asset objects; generating an asset container group by dividing the asset container into the asset container group based on an association relationship between the asset objects, wherein the association relationship defines correspondences between each asset container in the asset container group and at least one other asset container in the asset container group; and performing the contract operation on the asset container group using a contract object.
 2. The computer-implemented method of claim 1, wherein the contract object comprises a declaration of an execution program and an operation instruction used to perform the contract operation on the asset container group, maintaining the association relationship of the asset container group.
 3. The computer-implemented method of claim 2, wherein the contract object comprises a code field that is used to maintain an execution code related to the execution program.
 4. The computer-implemented method of claim 2, wherein the operation instruction comprises at least one of a transfer instruction and a transaction instruction for at least one of the asset objects.
 5. The computer-implemented method of claim 1, wherein the association relationship comprises a relationship of a hierarchical structure.
 6. The computer-implemented method of claim 1, wherein the asset container comprises a data table of a predetermined structure.
 7. The computer-implemented method of claim 1, wherein the blockchain network comprises a consortium chain, and the target user in the blockchain network is a consortium member that has asset object generation authority in the consortium chain.
 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising: receiving, from a target user recorded in a distributed database of a blockchain network, a user input comprising a request to perform a contract operation on asset objects comprising digital assets corresponding to physical assets associated with the target user; in response to receiving the request, generating an asset container as an operation target of the contract operation, the asset container recording field information of the asset objects; generating an asset container group by dividing the asset container into the asset container group based on an association relationship between the asset objects, wherein the association relationship defines correspondences between each asset container in the asset container group and at least one other asset container in the asset container group; and performing the contract operation on the asset container group using a contract object.
 9. The non-transitory, computer-readable medium of claim 8, wherein the contract object comprises a declaration of an execution program and an operation instruction used to perform the contract operation on the asset container group, maintaining the association relationship of the asset container group.
 10. The non-transitory, computer-readable medium of claim 9, wherein the contract object comprises a code field that is used to maintain an execution code related to the execution program.
 11. The non-transitory, computer-readable medium of claim 9, wherein the operation instruction comprises at least one of a transfer instruction and a transaction instruction for at least one of the asset objects.
 12. The non-transitory, computer-readable medium of claim 8, wherein the association relationship comprises a relationship of a hierarchical structure.
 13. The non-transitory, computer-readable medium of claim 8, wherein the asset container comprises a data table of a predetermined structure.
 14. The non-transitory, computer-readable medium of claim 8, wherein the blockchain network comprises a consortium chain, and the target user in the blockchain network is a consortium member that has asset object generation authority in the consortium chain.
 15. A computer-implemented system, comprising: one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform operations comprising: receiving, from a target user recorded in a distributed database of a blockchain network, a user input comprising a request to perform a contract operation on asset objects comprising digital assets corresponding to physical assets associated with the target user; in response to receiving the request, generating an asset container as an operation target of the contract operation, the asset container recording field information of the asset objects; generating an asset container group by dividing the asset container into the asset container group based on an association relationship between the asset objects, wherein the association relationship defines correspondences between each asset container in the asset container group and at least one other asset container in the asset container group; and performing the contract operation on the asset container group using a contract object.
 16. The computer-implemented system of claim 15, wherein the contract object comprises a declaration of an execution program and an operation instruction used to perform the contract operation on the asset container group, maintaining the association relationship of the asset container group.
 17. The computer-implemented system of claim 16, wherein the contract object comprises a code field that is used to maintain an execution code related to the execution program.
 18. The computer-implemented system of claim 16, wherein the operation instruction comprises at least one of a transfer instruction and a transaction instruction for at least one of the asset objects.
 19. The computer-implemented system of claim 15, wherein the association relationship comprises a relationship of a hierarchical structure.
 20. The computer-implemented system of claim 15, wherein the asset container comprises a data table of a predetermined structure. 